What a good design review sounds like

I have sat in a lot of design reviews that ended with everyone agreeing and nothing changing. The tell is almost always in the language. A review that improves work sounds different from a review that ranks it, and you can hear which one you are in within about four minutes.

The phrases that help

"What is this screen for?" — asked genuinely, not rhetorically. Half the problems in a review dissolve the moment somebody says the job out loud and the room realises two people had different jobs in mind.

"Show me the state where it goes wrong." Every design looks good with three well-behaved rows in it. The empty state, the error, the row with a forty-word name, the account with nine hundred entries — that is where the design either holds or falls over, and it is where nobody wants to spend the meeting.

"What did you try that did not work?" This one changes the temperature of a room more than any other. It moves the presenter from defending an outcome to narrating a process, and it stops the reviewers from suggesting the three things that were already tried and discarded last Tuesday.

The phrases that do not

"I would have done it differently" is not feedback, it is a fact about you. "It feels off" is a real signal and a useless one — the work is to spend the next thirty seconds finding out what is off, out loud, in front of everyone, even if you get it wrong.

A reviewer's job is not to have the taste. It is to make the taste in the room legible to the person holding the file.

And the last one, which took me too long: someone has to say what happens next. Not "great, thanks" — an actual sentence about which of the fifteen things said in the last hour the designer should act on. Without it, every review is advisory, and advisory reviews are the reason people stop bringing work in early.